[skip-changelog] Bump setup-protoc to v2 #2190
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alessio-perugini
force-pushed
the
bump-setup-protoc-to-v2
branch
4 times, most recently
from
1bcb455 to
264a1e5
Compare
alessio-perugini
added
topic: infrastructure
alessio-perugini
force-pushed
the
bump-setup-protoc-to-v2
branch
from
6904882 to
264a1e5
Compare
alessio-perugini
force-pushed
the
bump-setup-protoc-to-v2
branch
from
264a1e5 to
6276fc6
Compare
MatteoPologruto
changed the title
MatteoPologruto
approved these changes
May 31, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
UPGRADING.mdhas been updated with a migration guide (for breaking changes)configuration.schema.jsonupdated if new parameters are added.What kind of change does this PR introduce?
Bump the setup-protoc action. This will enable us to use the latest protobuf versions in the future
What is the current behavior?
What is the new behavior?
Does this PR introduce a breaking change, and is titled accordingly?
Other information